The ProjectWise Server installer opens.

The default installation location is C:\Program Files\Bentley\ProjectWise.

The option to change the installation location is hidden if another application from this release is already installed.

• Component Services EC plugin - Required for using Bentley OpenPlant with this server. Installing this feature creates a website in IIS called "Component Services".
• Automated File Processing > Full Text Indexing - Required for performing full text extractions.
• Automated File Processing > File Property and Thumbnail Image Extractors - Required for performing file property and thumbnail image extractions.

The location you specify is added to this server's DMSKRNL.CFG file under the section labeled, "Section defines allowable locations for storage areas". For example:

; -------------------------------------------------------------
; Section defines allowable locations for storage areas
; -------------------------------------------------------------

[FileStorageService]
StorageLocation0=E:\pwstorage

When you eventually create your storage areas for this server in ProjectWise Administrator, you will only be able to create a storage area if the location you select is somewhere within the allowable storage location.

This is the same user account you set up in the section, Before You Install or Upgrade ProjectWise Design Integration Server. If the user is a Windows account, enter the name of the domain to which the user belongs in the Domain Name field. If the user is a local account, enter the user’s computer name in the Domain Name field.

You can connect to the selected database using either an ODBC data source or a direct database connection.

Using an ODBC connection assumes that you have already created an empty database in SQL Server, and that you have already created a 64-bit ODBC data source on this computer that connects to the empty database in SQL Server. (See Before You Install or Upgrade ProjectWise Design Integration Server.)

If you are going to use a direct database connection, either you can create the empty database in SQL Server before installing this server, or you can use the Orchestration Framework Database Setup dialog to create a new database in SQL Server.

Left: connecting to SQL Server using an ODBC data source; Right: connecting to SQL Server using a direct database connection

To connect using an ODBC data source:

1. Set Connection Type to ODBC.
2. Select the ODBC data source you created for this purpose from the ODBC Connection list.
3. In the Database Security section, select the same authentication method that you configured the selected ODBC data source to use.

   If you select Use Windows authentication, you must already be logged in with a Windows account that is able to log in to the database that the ODBC data source points to.

   If you select Use SQL Server authentication, enter the User name and Password of the SQL Server account that the ODBC data source is configured to log in to the database with.

4. Click Test Data Source to make sure the specified Windows or SQL Server account can connect to the selected ODBC data source, and ultimately, the SQL Server database.

   If the specified account is able to connect, a dialog opens with the message, TEST COMPLETED SUCCESSFULLY!!

   Once connected, the Database Status field informs you that the database pointed to by the ODBC data source needs the latest Orchestration Framework database schema.

5. Click OK to install the latest Orchestration Framework database schema into the database.

To use a direct database connection:

1. Set Connection Type to Direct Database Connection.
2. In the Database Server field, enter name of the computer where SQL Server is installed.

   This field defaults to the local computer name. If your SQL Server installation has named instances, enter the name of the computer, followed by a backslash, followed by the SQL Server instance name you want to connect to. For example: computername\SQLServerinstancename

3. In the Database Security section, select the authentication method and account that you want to use to connect to the database.

   The account you specify here must be the same account you specified on the Orchestration Framework Configuration page of this server installer.

   If you select Use Windows authentication, you must already be logged in with a Windows account that is able to log in to the specified SQL Server instance.

   If you select Use SQL Server authentication, enter the User name and Password of a SQL Server account that is able to log in to the specified SQL Server instance.

   Tip: To quickly verify that the specified account can connect to SQL Server, try to select the Database list. If connection is successful, the list will be populated with databases. If connection is not successful, you will get an error and the list will be empty. If that is the case, one of the following may be true:

   • The service for the specified SQL Server instance may not be running. Make sure that it is running, then try again.
   • The SQL Server computer name specified, or instance name, or both, may be incorrect. Make sure you typed the names correctly, then try again.
   • The account you are trying to use does not exist in SQL Server. Make sure this account (whether local or Windows) exists in SQL Server with appropriate database permissions, then try again.
4. Once you have established a connection to SQL Server, the next step is to either create a new database in it, or select an existing empty database:

   Click the New button next to the Database list, then in the Create Database dialog, enter a name for the database and click OK. The database is added to SQL Server and selected in the Database list.

   or

   If you already have an empty database in SQL Server, select that database from the Database list.

   The Database Status field informs you that the selected database needs the latest Orchestration Framework database schema.

5. Click OK to install the Orchestration Framework database schema into the selected database.

1. Open the Product Activation Wizard to configure licensing for this server.
2. Manually start the service for ProjectWise Design Integration Server ('ProjectWise Integration Server') in the Services window.
3. If you specified to use Windows authentication in the Orchestration Framework Database Setup dialog (step 8 above), you must do ONE of the following extra steps (these steps are not required if you are using SQL Server authentication for your Orchestration Framework database connection).
   • Make sure that the service for ProjectWise Design Integration Server is running under an account that has read/write access to the Orchestration Framework database. To change the server account, right-click the ProjectWise Integration Server in the Services window and on the Log On tab, select This account and then specify a user account that has read/write access to the Orchestration Framework database. (By default, the ProjectWise server is set to run under the local system account, and this will not work when using Windows authentication for your Orchestration Framework database connection.)

     or

   • Leave the account that the ProjectWise server is set to run under as it is, and instead change the account that just the DmsAfpHost.exe process runs under. To change this account:
     1. Open the local Component Services window.
     2. Navigate to Component Services > Computers > My Computer > DCOM Config.
     3. Right-click FtrQueryForwarder (which controls DmsAfpHost.exe).
     4. On the Identity tab, select This user and then specify a user account that has read/write access to the Orchestration Framework database.
     Note: If you change the account that the DmsAfpHost.exe process runs under, make sure this account has write access to the C:\Program Files\Bentley\ProjectWise\bin\DmsAfpEngineConf.xml file.